Fortinet FortiGate appliances (hardware) End of Life (EOL) Dates & Support Timeline

Fortinet FortiGate appliances (hardware) lifecycle status — the real story

Fortinet FortiGate appliances are the firewall hardware under FortiOS: the FortiGate desktop, mid-range, high-end and chassis models, the FortiWiFi models with built-in wireless, and the FortiGate Rugged industrial models. Cycles on this page are appliance models, so it is the hardware companion to the FortiOS software page; the exploited FortiOS CVEs that put Fortinet firewalls in CISA's KEV catalog are software CVEs and are tracked there, but they run on these boxes. Every date comes from the Hardware & VM tab of Fortinet's own public Product Life Cycle page (no login), read twice: the page's public lifecycle endpoint and Fortinet's Hardware RSS feed, with every cell identical. The verifier re-reads the endpoint and a vendor sentinel re-reads the RSS feed at every build.

Field mapping, in Fortinet's own words from that page: support is the End of Order (EOO) Date, 'the last date on which a hardware or software product may be ordered'; eol is the End of Support (EOS) Date: 'After this date, Fortinet will not sell, manufacture, or improve the product and is under no obligation to provide support services.' The Last Service Extension Date (LSED), 'the last date at which an order will be accepted ... for an extension of an existing contract for support or security subscription services', which Fortinet sets 12 months before the EOS date, is carried as lastServiceExtension, and the Last Supported Software Version (LSSV) is carried verbatim where Fortinet prints one. Fortinet prints no launch date for hardware, so releaseDate is empty.

Fortinet's list is SKU-level. Each cycle is one model and holds every printed SKU row of that model whose four cells are identical (regional, government, DC-power, PoE and similar variants such as -LENC, -USG, -DC, -POE); a variant whose cells differ is served as its own cycle under its printed name, and the SKUs a cycle holds are listed with it. FortiGate-VM, FortiOS-VM and other virtual or licence rows, and the FortiController and FortiSwitch rows that Fortinet files in the same category, are not modelled here.

Fortinet lists a model only once it has an end-of-life notice. Current models without one (for example the FortiGate-40F) are not on Fortinet's list and are not listed here; their absence is not a statement that they are supported indefinitely.

Fortinet FortiGate appliances (hardware) release and support pattern

Of the 329 release lines tracked, 214 are past end of life and 115 are still within support. The next scheduled end of life is FortiGate-81E on November 14, 2026 — 28 days from this build. The longest-supported line currently published is FortiGate-3301E, to January 13, 2032.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

What does Fortinet FortiGate appliances (hardware) end of life mean for your organization?

When a version of Fortinet FortiGate appliances (hardware) reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.

Organizations running EOL Fortinet FortiGate appliances (hardware) should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when Fortinet FortiGate appliances (hardware) reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Fortinet FortiGate appliances (hardware) versions. This is a bridge, not a permanent solution — plan your migration in parallel.

Related Products